Rendered Jinja params for system props in control implementation statements #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for Jinja parameter substitution in component control implementations. The support is currently only for
system
object parameters.Purpose is to be able to include the System Title (and other system-specific information) within a control implementation statement that rendered in the System Security Plan.
Change accomplished by selectively adding a
statement.body_rendered
property. Thebody_rendered
property is added in two places:control_implementation_as_dict
's combined statement that is used to display the control implementation statements in the System Security Plan output templates.This approach nicely allows components to contain the Jinja parameter double brace template parameters (e.g.,
{{ system.root_element.title }}
).Todo:
Screenshots
in the System control implementations statements
in the System control implementation statement editing, the Jinja double brace parameter still appears
In the rendered SSP